home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #2
/
Monster Media No. 2 (Monster Media)(1994).ISO
/
bbs_util
/
nxmg_0_0.zip
/
NXOS.DES
< prev
Wrap
Text File
|
1994-05-02
|
8KB
|
210 lines
This is the combined doc for NXOS, NXMSGS, and NXLOGON..I'm too lazy to
seperate them.
NXOS, NXMSGS, and NXLOGON are copyright 1993-94 by Jason Baginski.
NXOS -- Remote DOS-like file-manager/BBS/whatever.
NXMSGS -- Remote graphical msg reader for XBBS style message bases.
NXLOGON -- Logon modual, to create dorinfoX.def file for NXOS and NXMSGS.
NXMSGS nad NXOS basicly rely on a DORINFOx.DEF file. This DORINFO file
*IS* modified! Instead of the "sysop name" NXOS/NXMSGS expects USER
ALIAS! I couldn't find a standard ascii door information file that
had alias in it, so, I had to..er..improvise.
The docs are simple, everything is a straight ascii config file type
thing..external programs(doors and such) are in a file called BATCH.BBS.
format of:
<name to run> <description>%<commands>
There are metacharacters in the command string that are:
%e - execute anything prior to %e, then go onto the rest of the line.
%n - node
%u - user name
%p - port
%b - baud
%a - user alias
%m - user name
%s - user security
And a couple others I don't quite remember... Here's my present BATCH.BBS
file(linewrapped around)
MSGS - NXMsg Message Reader%cd\NXOS\%eNXMSGS.EXE %n C:\XBBS\MSGS
PICT - Pictdoor Ansi Art Gallery%copy c:\nxos\dorinfo%n.def
c:\xbbs\dorinfo1.def%ecd\games\doors\pict\%epictdor
MECH - Mechwars Game%copy c:\nxos\dorinfo%n.def
c:\games\doors\mech\dorinfo.def%ecd\games\doors\mech%emw
ARENA - Arena Combat Game%copy c:\nxos\dorinfo%n.def
c:\games\doors\arena\dorinfo1.def%ecd\games\doors\arena%earena
Makes for very easy doors if you can write a batch file. :)
Yes, notice that the message reader IS an external program to NXOS, NXOS
itself is just a file area manager, NXLOGON is a userbase checking/logon
modual(which writes a DORINFO?.DEF file that all the other moduals read),
NXMSGS is my XBBS reader. Yup, this means that if you hated my logon
modual, or didn't like something in the message reader(like..er ANSI for
instance), you just change out that modual. Heck, I had a couple of people
that where interested in just the NXOS.EXE part so they could run it under
Maximus, another who wanted to run NXMSGS under RA. I guess no one liked my
logon modual..<sniff> <sniff>
Protocols are done simularly like the externals, except instead of a full
name, you have a single letter...here's my protocol.bbs
Z - Zmodem w 32bit CRC%pcz %p %b f sz r
Y - Ymodem%pcz %p %b f sy
S - Sealink%pcz %p %b f ss
1 - Xmodem 1K%pcz %p %b f s1
X - Xmodem%pcz %p %b f sx
All file descriptions are done through standard FILES.BBS files, directory
descriptinos are done in DIRS.BBS files. All very straight forward where you
have <filename or dir> <descript> one per line. In sysop mode, NXOS also
uses DESCRIPT.ION for its file/dir listings.
Notice how easy downloading is? Just "copy <filename>". I'll probably get
around to making drive U:, where people can upload by going
"copy U:<filename> C:" or download by "copy <filename> U:". As of the moment,
there are no commands for uploading....but when you think about how I designed
this thing, if some sysop wanted his BBS to allow uploads, he could just make
a BATCH.BBS that contains something like..
UPLOADZ - Send me a file with Zmodem%cd\uploads%epcz %p %b f rz r
<grin>
When you start up NXOS, on the command line, you pass what directory to start
out in, and it makes that directory C:\ to users and will not let them get any
higher out of that(they can go to sub-dirs, but nothing the other direction
higher than the start directory). When someone gets the sysop password
correctly, then the prompt shows the 'real' directory and lets you move all
around the drive(as well as gives you those commands listed in the help file
marked with '*'). So, basicly, you limit your users to sub-directories.
When users change their prompt(you did know you could do that, right?), it
creates a file for them called AUTOEXEC.nnn where nnn is the users number in
hex. Presently, I only have two things setup that AUTOEXEC can store...the
users prompt and the possibility of individual user BATCH.BBS files(for
cosysops or whatever), here's an example of one persons AUTOEXEC file...
PROMPT $P\ EH?$G
BATCH C:\NXOS\DAVID.BBS
BTW: here's the list of meta characters for PROMPT:
$P Path/Directory
$G '>'
$Q '='
$$ '$'
$T Time of day
$D Date
$V NXOS Version
$N 'C'
$L '<'
$B '|'
$_ newline
$E Esc(ascii 27)
$H Backspace
$U User name
$A User alias
$S User security
For NXMSGS, it uses a file called NXMSGS.CFG, just contains external editor
strings(uses same translations as BATCH.BBS/PROTOCOL.BBS), local editor,
origin line, color schemes(any ansi commands allowed), and to force color/
mono/or detect.
EDITOR quicked %p %b 180 180
LOCALEDITOR q msgtmp
ORIGIN This is an origin..cool.
COLOR_CURSOR
COLOR_HEADER1
COLOR_HEADER2
COLOR_HEADER3
COLOR_STATUS
COLOR_COMMAND
COLOR_MAIN
COLOR_CHAT
COLOR_HELP
FORCE COLOR
Oohh..and EVERYTHING is MASSIVELY multinode aware. It constantly checks for
message files from nodes to nodes and displays them if it gets them. I keep
forgetting to put in the support for the ECHO command, where you can send
messages/files to other nodes.
Here's my batch file I use to run NXOS, notice that I clean up the directories
for the heck of it, nothing will choke if you don't.. I use xu to hang
up the phone, by default, NXOS leaves the port "hot" on exit so you can
go back to a menuing program or a calling BBS easily..
cd \nxos
del dorinfo0.def
del msgtmp
NXLOGON %1 %2 0
NXOS 0 PASSWOD c:\misc
del dorinfo0.def
del msgtmp
xu dtr:2:off
xu dtr:2:on
xu dtr:2:off
Command line format:
NXLOGON <port> <baud> <node>
NXOS <node> <sysop password> <start dir>
NXMSGS <node> <path to XBBS style message bases> <path/name of area cfg>
If its any interest, it took me under a week to write all this junk, and as
such, it still needs a lot of work. Mostly I need to SEVERLY clean up the
message reader(if you couldn't tell, its slow/buggy, doesn't have very many
features, the most notable missing feature is new mail check). A couple
people have expressed an interest in me changing over NXMSGS to squish before
they'd run it. Not very many people have commented on NXOS itself, I've fixed
most of what they've told me to do. If you can think of anything, shoot it my
way...
Oh, just to let you know how "inefficient" everything is..
batch.bbs 456 5-02-94 18:12
nxlogon.exe 12939 3-15-94 6:16
nxmsgs.cfg 296 4-20-94 0:05
nxmsgs.exe 19901 5-02-94 14:43
nxos.exe 18668 4-12-94 19:21
nxuser.hlp 1264 1-05-94 11:32
protocol.bbs 157 5-02-94 17:46
quicked.cfg 532 11-09-93 16:22
users.nx 100969 5-01-94 22:07 (about 900 users)
welcome.asc 418 12-10-93 1:03
The biggest exe takes about 68K while running.
NXOS and NXMSGS are shareware, 10 bucks each. 40 day evaluation period.
Registration gets you..er..well..er..nothing really. It simply allows you
to run the software past its evaluation period. If I caught someone
running either past the 40 day evaluation period, I'm going to be mighty
peeved at you! Payment is accepted in check or money order _only_, don't
send me cash..there are too many prozac'd mail workers who like loose
change. Make checks/money orders/whatever out to "Jason K Baginski".
NXLOGON is _free_..you may modify it all you like, but, do *NOT* release
those modifications without express premission from the original author
and copyright holder, Jason Baginski. Shoot me off some netmail or something
explaining the changes, or send me the changes, or whatever, and we'll see
what happens.
Send comments/suggestions/registrations/first borns by snailmail to:
Jason K Baginski
1749 E 61st
Tulsa, OK 74136
Or netmail me at Fidonet#1:170/906.0
Revision History:
NXOS v0.0--Released 05-02-94
Default stuffin.
NXMSGS v0.0--Released 05-02-94
Default stuffin.
NXLOGON v0.0--Released 05-02-94
Default stuffin.